Stackit changes#11208
Conversation
katarzyna-koltun-mx
left a comment
katarzyna-koltun-mx
left a comment
There was a problem hiding this comment.
Reviewed and waiting for the go ahead.
| | User | Username for the registry robot account | | ||
| | Password | Token (password) for the robot account | | ||
|
|
||
| Before pushing images to container registry, you must first create the repository. |
There was a problem hiding this comment.
I think repositories automatically created when pushing to them.
There was a problem hiding this comment.
@walkline https://mendix.slack.com/archives/C0B2Y7ZQ3K4/p1778569861394009
here, gauarav created the registry before
and then u were able to use it
There was a problem hiding this comment.
fixed. Replaced repository with registry
| Example: | ||
|
|
||
| ```shell | ||
| kubectl patch serviceaccount default -n <namespace> -p '{"imagePullSecrets": [{"name": "<secret-name>"}]}' |
There was a problem hiding this comment.
Maybe we should mention somewhere that mxpc-cli or the Helm chart will create a secret with the registry credentials, so they can use that secret. Usually, the secret has a name similar to this: mendix-generic-registry-secret.
| If your provider is Azure, [Postgres managed identity authentication](#database-postgres-azwi) can be used instead to increase security. | ||
|
|
||
| {{% alert color="info" %}} | ||
| The Mendix on-demand PostgreSQL provisioner cannot be used directly. STACKIT PostgreSQL Flex does not expose the `CREATEROLE` privilege, which is necessary for Mendix to automatically create database users with SQL commands. In order to facilitate the use of Postgres, switch to [JDBC plan](#database-jdbc) and create a dedicated database user for the new Mendix environment using the STACKIT CLI or API. |
There was a problem hiding this comment.
Maybe we should add something like this at the beginning: This limitation applies only to STACKIT PostgreSQL Flex databases. Because Reading just the first santace can lead to a false impression.
|
|
||
| #### Prerequisites | ||
|
|
||
| * A Ceph or S3-compatible bucket. |
There was a problem hiding this comment.
Why are we mentioning Ceph storage here (and several lines below)? I only tested the S3-compatible interface for STACKIT Object Storage.
There was a problem hiding this comment.
This was already there
I just moved ceph storage in next section
|
|
||
| #### Configuring the Plan | ||
|
|
||
| In the Ceph plan configuration, enter the following details: |
| {{% /alert %}} | ||
|
|
||
| {{% alert color="info" %}} | ||
| The Mendix on-demand PostgreSQL provisioner cannot be used directly. STACKIT PostgreSQL Flex does not expose the CREATEROLE privilege, which is necessary for Mendix to automatically create database users via SQL commands. Hence, a databaser user needs to be created per environment before deployment. |
There was a problem hiding this comment.
The same comment: Maybe we should add something like this at the beginning: This limitation applies only to STACKIT PostgreSQL Flex databases. Because Reading just the first santace can lead to a false impression.
…n' into stackItdocumentation emote commit for stackit
walkline
left a comment
walkline
left a comment
There was a problem hiding this comment.
Looks good to me, thanks!
|
On hold until June, waiting for the go ahead |
3 participants
Stack it changes